found old installation exchange in DC.

Delete  with ADSIEdit:
CN=Microsoft Exchange
CN=Microsoft Exchange ... Objects
other path not found

but this not help me..

get error again: [ERROR] "d2.domain.root" isn't a valid SMTP domain.

Where can I find the problem?

System for new exchange server - clear with windows 2012 R2  standard

• Edited by YuriyTN Wednesday, June 03, 2015 12:09 PM

not help ((

i'm deleted in CN=Services,CN=Configuration,DC=DOMAIN,DC=ROOT:
CN=Microsoft Exchange
CN=Microsoft Exchange Autodiscover - not found
in CN=Extended-Rights,CN=Configuration,DC=DOMAIN,DC=ROOT:
all with CN=ms-Exch-*,
and: CN=Exchange-Information , CN=Exchange-Personal-Information

but this not help me (

message from event apps:

Log Name: Application
Source: MSExchange ADAccess
Date: 10/06/2015 14:22:36
Event ID: 4027
Category tasks: (1)
Level: Error
Keywords: Classic
User: N / A
Computer: exch.domain.root
Description:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


If the event originated on another computer, you may need to save the displayed information with the event.

The following information was included with the event: 

ExSetupUI.exe
 3868
 Get Servers for domain.root
 TopologyClientTcpEndpoint (localhost)
 3
 System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0038715. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    --- End of inner exception stack trace ---

any idea?

You have an Exchange server and you removed the organization?  That wouldn't be a good thing.  You said you don't have an existing server.

Hi Yuriy,

Thank you for your question.

We could open register on DC then navigate to the following path to check if the value is existed:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\NV Domain and

HKEY_LOCAL_MACHINE \System\CurrentControlSet\Services\Tcpip\Parameters\Domain

If the value is not existed, we could refer to the following link to add it:

https://technet.microsoft.com/en-us/library/aa998420(v=exchg.80).aspx

Then we checked the msDS-AllowedDNSSuffixes attributes on Domain object container. If it is empty, we could add domain name in that and then force AD replication.

Then we re-run setup to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\NV Domain

and

HKEY_LOCAL_MACHINE \System\CurrentControlSet\Services\Tcpip\Parameters\Domain

value = domain.root

msDS-AllowedDNSSuffixes attributes  was empty.

set domain.root

not help ((

Hi YuriyTN,

Open the following link to check if there is certificate in ADSIEDIT.MSC, remove it then check if the issue persist:

https://technet.microsoft.com/en-us/library/gg685518.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim